CVE-2021-45492

CVE-2021-45492 affects Sage 300 ERP (through 6.8.x). The installer places C:\Sage\Sage300\Runtime at the front of the system PATH, and this directory is writable by unprivileged users due to weak C:\ permissions inherited by the installer. Because PATH entries are used for DLL search order, an at...

CVE-2022-38583

The vulnerability CVE-2022-38583 affects Sage 300 2017–2022 (6.4.x–6.9.x) in Windows Peer-to-Peer or Client-Server configurations. A low-privilege Sage 300 workstation user can access the server’s SharedData folder to view or modify credentials for Sage 300 users and SQL accounts, enabling impers...

CVE-2022-41398

CVE-2022-41398 affects Sage 300 (through 2022) where the optional Global Search feature configures Apache Solr with hard-coded admin credentials. This enables login to the Solr dashboard with admin privileges and potential exposure of sensitive data. The Red Hat/Red flags and other records corrob...

CVE-2022-41397

CVE-2022-41397 concerns Sage 300 (through version 2022) where the optional Web Screens and Global Search features use a hard-coded 40-byte Blowfish key, “LandlordPassKey,” to encrypt/decrypt secrets stored in configuration files and in database tables. This key is embedded in the feature’s encryp...

CVE-2023-29927

CVE-2023-29927 affects Sage 300 up to 2022. The issue is that role-based access controls are enforced only on the client side, enabling low-privilege users—especially on workstations in Windows Peer-to-Peer or Client-Server Sage 300 configurations—to recover SQL connection strings and directly in...

CVE-2022-41399

The CVE-2022-41399 issue affects Sage 300 (through 2022) where the optional Web Screens feature uses a hard-coded 40-byte Blowfish key (PASS_KEY) to encrypt/decrypt the PORTAL database connection string in dbconfig.xml. This cryptographic weakness could allow an attacker to access the SQL databas...

CVE-2022-41400

Sage 300 (through 2022) is affected by CVE-2022-41400 due to a hard-coded 40-byte Blowfish key used to encrypt/decrypt user passwords and SQL connection strings stored in ISAM database files in the shared data directory. This weak key mechanism could allow an attacker to decrypt credentials store...